System and method for maintaining data connectivity over a satellite link

ABSTRACT

A system for maintaining data connectivity in a satellite communications system including a satellite terminal with a ping mechanism, a satellite ground station, and a ping server, where the ping mechanism pings the ping server and restores data connectivity between the satellite terminal and the satellite ground station.

BACKGROUND

In a satellite-based communications system, it may be difficult todetermine if a satellite link is fully functional end-to-end withoutsending data across the satellite link. Algorithms exist to monitor andhandle the various conditions that may impair the ability to send dataover a satellite link, but these algorithms may be complex and hard todevelop and test. The algorithms may also rely on the user equipmentthat is attached to a satellite terminal to function, which may makethem unreliable.

BRIEF SUMMARY

An example system for maintaining data connectivity in a satellitecommunications system includes a satellite terminal including a pingmechanism, a satellite ground station, and a ping server, where the pingmechanism pings the ping server and restores data connectivity betweenthe satellite terminal and the satellite ground station.

BRIEF SUMMARY OF THE DRAWINGS

FIG. 1 depicts an exemplary system for maintaining data connectivityover a satellite link;

FIG. 2 depicts an exemplary state diagram for a system for maintainingdata connectivity over a satellite link;

FIG. 3 depicts an exemplary procedure for entering an active ping state;

FIG. 4 depicts an exemplary procedure for active pinging;

FIG. 5 depicts an exemplary procedure for recovering a connection;

FIG. 6 depicts an exemplary procedure for checking and handling dataconnectivity errors;

FIG. 7 depicts an exemplary procedure for determining if a connection isalways on; and

FIG. 8 depicts an exemplary procedure of an active scan for an always onconnection.

Additional features and advantages are described herein, and will beapparent from the following Detailed Description and the figures.

DETAILED DESCRIPTION

FIG. 1 depicts an exemplary system for maintaining data connectivityover a satellite link. The system may include a satellite ground station(or hub) 101, a satellite terminal 102, a satellite 103, a network 104,a data server 105, a ping server 106, and user equipment 107.

The satellite ground station 101 may be a hub or gateway for a satellitecommunications system, and may be connected to the satellite terminal102 through the satellite 103. The satellite ground station 101 may be,for example, a high capacity, large antenna earth station withconnectivity to ground telecommunications infrastructure. Feeder linksmay carry data between the satellite ground station 101 and thesatellite 103, and may include a forward uplink for transmitting datafrom the satellite ground station 101 to the satellite 103, and a returndownlink for transmitting data from the satellite 103 to the satelliteground station 101. User broadband links may carry data between thesatellite 103 and the satellite terminal 102, and may include a returnuplink for transmitting data from the satellite terminal 102 to thesatellite 103, and a forward downlink for transmitting data from thesatellite 103 to the satellite terminal 102. The user broadband linksmay enable the provision of broadband service to the satellite terminal102.

The satellite terminal 102 may be, for example, a Very Small ApertureTerminal (VSAT), which may be used by end users to access the satellitecommunications system. The satellite terminal 102 may include a remotesatellite dish for receiving RF signals from, and transmitting RFsignals to, the satellite 103, a satellite modem and other equipment formanaging the sending and/or receiving of data, and may be connected tothe user equipment 107, which may be computer systems or otherelectronic devices capable of network communications at a site remotefrom the satellite ground station 101. For example, the satelliteterminal 102 may be used at a residence or place of business to provideaccess to the network 104, which may be for, example, the Internet. Thesatellite terminal 102 may also be used at an unmanned remote location,and may be used to provide machine to machine or SCADA communication tothe user equipment 107. A communications stack 110 may be part of thesatellite terminal. The communications stack 110 may be the set of, forexample, drivers, libraries, processes, and protocols on the satelliteterminal 102 responsible for establishing and using the data connectionbetween the satellite terminal 102 and the satellite ground station 103.

The satellite 103 may be any suitable communications satellite forconnecting the satellite ground station 101 to the user equipment 107.The satellite 103 may use spot beams, frequency reuse, and/orpolarization reuse to maximize the total capacity of the system. Signalspassing through the satellite 103 in the forward direction, towards thesatellite terminal 102, may be based on the DVB S.2 standard (ETSI EN302 307) using signal constellations up to and including at least16-APSK. The signals intended to pass through the satellite 103 in thereturn direction, toward the satellite ground station 101, may be basedon the IPoS standard (ETSI TS 102 354). Other suitable signal types mayalso be used in either direction, including, for example higher datarate variations of DVB S.2, or satellite systems based on the InmarsatAir Interface or GeoMobile Radio Services standards.

The satellite ground station 101 may be connected the network 104, whichmay be, for example, a private network and/or the Internet. The userequipment 107 connected to the satellite terminal 102 may connect to thenetwork 104 through the satellite 103 and the satellite ground station101. Data sent from the satellite terminal 102 to the network 104 may betransmitted to the satellite 103 on the return uplink, then from thesatellite 103 to the satellite ground station 101 using the returndownlink. The satellite ground station 101 may then transmit the data tothe network 104. Data from the network 104 may be sent the satelliteterminal 102 by being transmitted to the satellite ground station 101,then to the satellite 103 on the forward uplink, and then to thesatellite terminal 102 using the forward downlink.

The data server 105 may be any suitable data server or servers. Forexample, the data sever 105 may be a data farm or a single specializedserver. The data server 105 may be connected to the satellite groundstation 101 through the network 104, which may be the Internet, and/ormay be a private network or a virtual private network (VPN).

The ping server 106 may be any suitable combination of hardware andsoftware for responding to active pings from the satellite terminal 102.The ping server 106 may be the same piece of equipment as the dataserver 105, co-located with the data server 105, or remote from the dataserver 105. The ping server 106 and data server 105 may also be part ofthe satellite ground station 101. Pinging the ping server 106 may allowthe satellite terminal 102 to test data connectivity between thesatellite terminal 102 and the data server 105 and to detect problemsthat might exist with the data connectivity. There may be more than oneping server 106 associated with the data server 105, and every pingserver 106 may have a separate Internet Protocol (IP) address.

The satellite terminal 102 may include a built in ping mechanism 108.The ping mechanism 108 may be any suitable combination of hardware andsoftware for performing pings to test for data connectivity between thesatellite terminal 102 and the data server 105, and for performingvarious recovery steps if data connectivity has been lost. The pingmechanism 108 may ping IP addresses associated with the ping server 106to test data connectivity between the satellite terminal 102 and thedata server 105. If data connectivity has been lost, the ping mechanism108 of the satellite terminal 102 may be capable of restarting theconnection or rebooting the satellite terminal 102, to attempt torestore data connectivity.

FIG. 2 depicts an exemplary state diagram for a system for maintainingdata connectivity over a satellite link. The ping mechanism 108 in thesatellite terminal 102 may transition between various states ofoperation depending on the current state of data connectivity and thesuccess or failure of various recovery mechanisms.

In a startup state 201, the satellite terminal 102 may be started, andmay establish data connectivity with the satellite ground station 101and the data server 105 through the satellite 103. The ping mechanism108's RAB error monitoring state 206 may also be entered concurrent withthe startup state 201, and may run concurrently with the other states ofthe ping mechanism 108. An RAB error monitor 109 may be a watchdogprocess running in the RAB error monitoring state 206 that monitorswhether the user equipment 107 requested data transfers from thesatellite terminal 102 succeed. If the RAB error monitor 109 detects anumber of errors in the data transfers, for example, six consecutiveerrors, the RAB error monitor 109 may send a “Restart” message to theother processes of the ping mechanism 108.

After the satellite terminal 102 has started up, the ping mechanism 108of the satellite terminal 102 may transition from the startup state 201to a ping idle state 202. In the ping idle state 202, the ping mechanism108 of the satellite terminal 102 may not be actively pinging the pingserver 106. A countdown timer may count down the time since the pingmechanism 108 entered the ping idle state 202 from the startup state201, from an active ping state 203, from a recover connection state 204,and/or from a RAB error monitoring state 206. The ping mechanism 108 maybe waiting for the occurrence of an event, such as, for example, theexpiration of the countdown timer, the passage of a set amount of timewithout the receipt of any incoming data from the satellite groundstation 101, and/or a “Restart” message from the RAB error monitoringprocess, to enter the active ping state 203.

When the ping mechanism 108 transitions from the ping idle state 202 tothe active ping state 203, the ping mechanism 108 may start activelypinging the ping server 106 to test the data connectivity. The pingmechanism 108 may cause the satellite terminal 102 to send out pingmessages, such as, for example, Internet Control Message Protocol (ICMP)pings, to the IP addresses for any number of ping servers 106. If thepinging is successful, for example, the ping servers 106 return anacceptable number of the ping messages back to the satellite terminal102, indicating that data connectivity still exists between thesatellite terminal 102 and the data server 105 through the satellite103, the ping mechanism 108 may re-enter the ping idle state 202. If thepinging is unsuccessful, for example, too few or none of the pingservers 106 return the ping messages to the satellite terminal 102, orthe ping mechanism 108 cannot find an active satellite connection, orPDP context, to send the ping messages out over, the ping mechanism 108may enter a recover connection state 204.

In the recover connection state 204, the ping mechanism 108 may attemptto restore data connectivity between the satellite terminal 102 and thedata server 105 through the satellite 103 and the satellite groundstation 101. The ping mechanism 108 may, for example, attempt to restartthe communications stack 110 of the satellite terminal 102, which mayforce the satellite terminal 102 to restart the satellite linkactivation sequence with the satellite ground station 101,re-establishing a connection with the satellite ground station 101through the satellite 103. If the stack restart completes successfully,the ping mechanism 108 may re-enter the ping idle state 202. If theattempt to recover the connection fails and reestablish dataconnectivity fails, for example, if the stack restart does not complete,the ping mechanism 108 may enter a reboot state 205.

In the reboot state 205, the ping mechanism 108 may force the satelliteterminal 102 to reboot itself. Once the satellite terminal 102 hasrebooted, the satellite terminal 102 may enter the startup state 201 andattempt to establish data connectivity with the data server 105.

FIG. 3 depicts an exemplary procedure for entering an active ping state.The active ping state 203 may be entered from the ping idle state 202under certain conditions. In block 301, the ping mechanism 108 may bestarted. For example, when the satellite terminal 102 starts, the pingmechanism 108 may enter the startup state 201. After startup hascompleted, the ping mechanism 108 may transition to the ping idle state202.

In block 302, the ping mechanism 108 may sleep, or idle, and wait toreceive incoming messages. For example, in the ping idle state 202, theping mechanism 108 may be idle, waiting to receive messages the mayindicate the need to enter the active ping state 203.

In block 303, the ping mechanism 108 may receive incoming messages.Messages may be sent to the ping mechanism 108 by, for example, the pingmechanism 108 itself, or by the RAB error monitor 109 portion of theping message.

In block 304, the ping mechanism 108 may check to see if the pingmechanism 108's timer has expired. The timer may be started, forexample, in block 311, after the ping mechanism 108 initially enters theping idle state 202, and may count down from the time since the pingmechanism 108 entered the ping idle state 202. If the satellite terminal102 receives incoming data from the satellite ground station 101, thetimer may be restarted. The expiration of the timer may indicate thatthe appropriate amount of time has passed since the last time the pingmechanism 108 entered the active ping state 203 and pinged the pingserver 106. The appropriate amount of time may be configurable, forexample, by a user, and may be used to set the amount of time betweenpings of the ping server 106. For example, if the timer is set to 30minutes, the ping mechanism 108 may enter the active ping state 203 onceevery 30 minutes. If the timer has expired, flow proceeds to block 305.Otherwise, flow proceeds to block 306.

In block 305, the ping mechanism 108 may send itself a “Do Ping”message. The ping mechanism 108 may send itself a “Do Ping” message toindicate that the ping mechanism 108 should transition to the activeping state 203 due to the timer's expiration. Flow may proceed fromblock 305 back to block 302 and then block 303, where the “Do Ping”message may be received. The timer may also be reset.

In block 306, the ping mechanism 108 may determine if a “Do Ping”message has been received? If the ping mechanism 108 has received a “DoPing” message, such as, for example, one generated in block 305, flowmay proceed to block 312. Otherwise, flow proceeds to block 307.

In block 307, the ping mechanism 108 may determine if an “Enable”message has been received. If the ping mechanism 108 has received an“Enable” message, for example, one sent during the startup state 201,flow proceeds to block 308. Otherwise, flow proceeds to block 309.

In block 308, the ping mechanism 108 may set the timer to theappropriate amount of time. The timer may be set by the ping mechanism108 to start counting down from the configured time between pings. Flowmay then proceed back to block 302.

In block 309, the ping mechanism 108 may determine if a “Disable”message has been received. If the ping mechanism 108 has received a“Disable” message, flow may proceed to block 310. Otherwise, flowproceeds to block 311.

In block 310, the ping mechanism 108 may stop the ping timer. Thetimer's countdown may be stopped by the ping mechanism 108, preventingthe timer from expiring. This may prevent the ping mechanism 108 fromentering the active ping state 203.

In block 311, the ping mechanism 108 may determine if a “Restart”message has been received. If the ping mechanism 108 has received a“Restart” message, for example, from a watchdog such as the RAB errormonitor 109, flow proceeds to block 312. Otherwise, flow proceeds backto block 302.

In block 312, the ping mechanism 108 may enter the active ping state203. For example, if either the timer has expired, or the ping mechanism108 has received a “Restart” message, the ping mechanism 108 may enterthe active ping state 203 to ping the ping server 106 and restart thecommunications stack 110 or reboot the satellite terminal 102, ifnecessary.

FIG. 4 depicts an exemplary procedure for active pinging. When the pingmechanism 108 of the satellite terminal 102 enters the active ping state203, the ping mechanism 108 may begin pinging the ping server 106, totest data connectivity between the satellite terminal 102 and the dataserver 105. In block 401, the ping mechanism 108 may start the procedurefor active pinging. The ping mechanism 108 may have transitioned intothe active ping state 203 from the ping idle state 202.

In block 402, the ping mechanism 108 may determine if a Packet DataProtocol (PDP) context is active. A data connection between thesatellite terminal 102 and the satellite ground station 101 may be a PDPcontext. If a PDP context is active, flow proceeds to block 403.Otherwise, if no PDP contexts are active, flow proceeds to block 416,and no pinging may be performed as there may be no connection availablefor the satellite terminal 102 to use to ping the ping server 106.

In block 403, the ping mechanism 108 may determine if a “Ping Required”flag has been set. The “Ping Required” flag may be set, for example, ifpinging is to be performed without checking whether the satelliteterminal 102 has recently been successful sending data to or receivingdata from the satellite ground station 101. Use of the “Ping Required”flag may reduce the number and frequency of pings performed by the pingmechanism 108, as no ping will be performed unless the “Ping Required”has been set. If the “Ping Required” flag is set, flow proceeds to block407, otherwise flow proceeds to block 404.

In block 404, the ping mechanism 108 may determine if the satelliteterminal 102 has successfully received data from or sent data to thesatellite ground station 101 recently. For example, the ping mechanism108 may check for the successful receipt or transmission of data withina configured amount of time, such as, for example, half of theperiodicity. If the satellite terminal 102 has successfully sent orreceived data within the configured time, flow proceeds to block 405.Otherwise flow proceeds to block 407.

In block 405, the ping mechanism 108 may reset all watchdog counters,error start times, and a backoff parameter. The backoff parameter may besaved in non-volatile memory on the satellite terminal 102. All of theconfigured parameters for the satellite terminal 102 may be stored innon-volatile memory, such as, for example, flash memory. The backoffparameter may be used to prevent the satellite terminal 102 fromflooding the network with signaling when the satellite terminal 102keeps getting rejected. For example, if the satellite terminal 102 isnot correctly configured or has an invalid subscription and getsrejected from connecting with the satellite ground station 101, thenincrementing of the backoff parameter on each rejection will cause anincrease (e.g., exponential) in the amount of time between attempts bythe satellite terminal 102 to try to access the network. For example,the amount of time between attempts may be up to 24 hours which mayresult in a misconfigured satellite terminal 102 backing off to tryingonce a day rather than every few minutes. The successful receipt ortransmission of data by the satellite terminal 102 within the configuredamount of time may indicate that the satellite terminal still has dataconnectivity, and therefore no pinging may be necessary. The pingmechanism 108 may reset any error counts, such as, for example, the RABerror monitor 108's count of data transmission errors, reset error starttimes, reset the backoff parameter, as no backoff may be needed, andsave information to the CIM preparation for transition back to the pingidle state 202.

In block 406, the ping mechanism 108 may reset the timer and enter theping idle state 202. Because the data connection is still active, nopinging may be necessary, so the ping mechanism 108 may leave the activeping state 203 and re-enter the ping idle state 202. The ping mechanism108 may also reset the timer used to countdown to the next time the pingmechanism 108 may enter the active ping state 203.

If the “Ping Required” flag is set and/or the satellite terminal 102 hasnot recently received data from or sent data to the satellite groundstation 101 the “Ping Failed” flag may be set in block 407. The “PingFailed” flag may indicate that attempts to ping the ping server 106 havefailed, and data connectivity has been lost. The “Ping Failed” flag maybe set before any pinging occurs and may be cleared if the pinging issuccessful.

In block 408, the ping mechanism 108 may retrieve the next availableaddress to ping. The ping mechanism 108 may have access to a list of IPaddresses, with each IP address corresponding to a ping server 106. Iffor example, no pinging has been attempted since the ping mechanism 108most recently entered the active ping state 203, the ping mechanism 108may retrieve the first IP address on the list of IP addresses. Afterpinging the first IP address, the ping mechanism 108 may retrieve thesecond IP address, and so on.

In block 409, the ping mechanism 108 may determine if the IP addressretrieved in block 408 is valid. The ping mechanism 108 may check the IPaddress to ensure that IP address conforms to known standards for IPaddresses, such as, for example, IPv4 and IPv6, and that the IP addressis an address external to the satellite terminal 102. For example, thesatellite terminal 102 may use the standard localhost IP address of127.0.0.1 to refer to itself. Thus, 127.0.0.1 may not be a valid IPaddress for pinging.

In block 410, the ping mechanism 108 may format and send the pingmessage. The ping mechanism 108 may attempt to ping the ping server 106using the IP address. For example, the ping mechanism 108 may send anICMP ping to the ping server 106 at the IP address. The ping message maybe sent out by the satellite terminal 102.

In block 411, the ping mechanism 108 may determine if the pinging wassuccessful. If the ping server 106 returned the ping message from thesatellite terminal 102, the pinging may be considered successful, andthe flow may proceed to block 414. Otherwise, if the ping message is notreturned, flow may proceed to block 412.

In block 412, the ping mechanism 108 may determine if the maximum numberof ping attempts have been made to the IP address. The ping mechanism108 may be configured to only ping each IP address a certain number oftimes if the successive ping attempts are not successful, beforedetermining that the IP address cannot be reached. If the ping mechanism108 has pinged the IP address the maximum number of times, flow proceedsto block 413. Otherwise, flow proceeds back to black 410, where the pingmechanism 108 may send out another ping message to the IP address.

In block 413, the ping mechanism 108 may determine if there are any moreIP addresses that can be pinged. There may be multiple ping servers 106,and each ping server may have its own IP address on the list of IPaddresses. If there are IP addresses on the list of IP addresses thathave not been pinged since the ping mechanism 108 most recently enteredthe active ping state 202, flow may proceed back to block 408 where theping mechanism 108 may retrieve the next IP address. Otherwise, flowproceeds to block 415.

In block 414, the ping mechanism 108 may clear the “Ping Failed” flag.If the pinging of the ping server 106 is successful, the ping attemptmay no longer be considered failed. The ping mechanism 108 may clear the“Ping Failed” to indicate that the pinging was successful. Flow thenproceeds to block 415.

In block 415, the ping mechanism 108 may determine if the “Ping Failed”flag is set. If the ping attempt was successful, the “Ping Failed” flagmay be cleared, for example, as in block 414, and flow proceeds to block405. If the ping attempt was unsuccessful, for example, none of the pingservers 106 at the pinged IP addresses returned the ping, flow proceedsto block 416.

In block 416, the ping mechanism 108 may enter the recover connectionstate 204. The ping attempt may have failed, and data connectivitybetween the satellite terminal 102 and the satellite ground station 101may need to be recovered. The ping mechanism 108 may enter the recoverconnection state 204 from the active ping state 203 to attempt torecover data connectivity.

FIG. 5 depicts an exemplary procedure for recovering a connection. Inblock 501, the ping mechanism 108 may enter the recover connectionsstate 204 and begin recovery of data connectivity.

In block 502, the ping mechanism 108 may determine if an error starttime is set to zero. The error start time may indicate the time at whichthe ping mechanism 108 entered the recover connection state 204 due to afailed ping attempt. If the error start time is set to zero, flowproceeds to block 503. Otherwise, flow proceeds to block 504.

In block 503, the ping mechanism 108 may set the error start time to thecurrent start time. Setting the error start time to the current starttime may store the time at which the ping mechanism 108 entered therecover connection state 204. Flow then proceeds to block 504.

In block 504, the ping mechanism 108 may determine if a PDP context isactive. If a PDP context is active, flow proceeds to block 505.Otherwise, if no PDP contexts are active, flow proceeds to block 510.

In block 505, the ping mechanism 108 may increment a restart stackcounter, and set a failure wait time to the current time. The restartstack counter may count the number of times the ping mechanism 108 hasattempted to restart the communication stack of the satellite terminal102.

In block 506, the ping mechanism 108 may determine if this is the firsttime the ping mechanism 108 has attempted to restart the communicationsstack 110 of the satellite terminal 102. If it is the first time, forexample, if the restart stack counter is set to one, flow proceeds toblock 507. Otherwise, flow proceeds to block 513.

In block 507, the ping mechanism 108 may restart the communicationsstack 110. Restarting the communication stack of the satellite terminal102 may force the satellite terminal 102 to re-establish a connectionwith the satellite ground station 101 through the satellite 103.

In block 508, the ping mechanism 108 may reset the ping timer (e.g. to 2minutes). The ping timer may be set to 2 minutes to allow enough timefor the communications stack 110 to be restarted before the pingmechanism 108 attempts to ping the ping server 106 again.

In block 509, the ping mechanism 108 may enter the ping idle state 202.

In block 510, the ping mechanism 108 may determine if the PDP contextthat was not active in block 504 was previously active. If the PDPcontext was not previously active, flow proceeds to block 513.Otherwise, flow proceeds to block 511.

In block 511, the ping mechanism 108 may increment a context activefailure counter. The context active failure counter may count the numberof times the previously active PDP context failed to be active whenchecked by the ping mechanism 108 in the recover connection state 204.

In block 512, the ping mechanism 108 may determine if the context activefailure counter is greater than one. If the context active failurecounter is greater than one, for example, the previously active PDPcontext has failed before, flow proceeds to block 505. Otherwise, flowproceeds to block 509 where the ping mechanism 108 may enter the pingidle state 202, allowing time for the satellite terminal 102 toautomatically attempt to reactive the PDP context, as discussed below inFIG. 8.

In block 513, the ping mechanism 108 may determine if too long an amountof time has passed from the error start time. The error start time maybe the time at which the ping mechanism 108 entered the recoverconnection state 204. If either the PDP context is not active and wasnot previously active, or if the restart stack counter is greater thanone, the ping mechanism 108 may then determine how much time has passedsince the ping mechanism 108 entered the recover connection state 204.The error start time may be compared to the current time, and if the gapbetween the two is long enough, flow proceeds to block 514. Otherwise,if not enough time has passed from the error start time to the currenttime, flow proceeds to block 509 where the ping mechanism 108 may enterthe ping idle state 202.

In block 514, the ping mechanism 108 may update the backoff parameter.The backoff parameter may be updated by, for example, incrementing thebackoff parameter. This may cause the satellite terminal 102 to waitlonger before attempting to connect to the satellite ground station 101the next time data connectivity is lost, preventing repeated failures torestore data connectivity, due to, for example, the satellite terminal102 being misconfigured, from causing the satellite terminal 102 toflood the network.

In block 515, the ping mechanism 108 may save the backoff parameter. Thebackoff parameter may be stored in flash memory, or any other suitablenon-volatile memory, on the satellite terminal 102, along with otherparameters for the satellite terminal 102, so that rebooting thesatellite terminal 102 does not reset certain parameters. Parametersstored in volatile memory may be reset when the satellite terminal 102is rebooted.

In block 516, the ping mechanism 108 may add a critical entry in thesyslog. The syslog may be a log of events that occur within thesatellite terminal 102, and particularly events relating to the overallstatus of the satellite terminal 102. The critical entry added to thesyslog may indicate that the ping attempt failed and efforts to restartthe communication stack were unsuccessful. The ping mechanism 108 maywait for a set period, for example, 5 clock tics, before writing thecritical entry to the syslog.

In block 517, the ping mechanism 108 may enter the reboot state 205. Ifother attempts at recovering data connectivity between the satelliteterminal 102 and the satellite ground station 101 have failed, thesatellite terminal 102 may be rebooted. Rebooting the satellite terminal102 may cause the satellite terminal 102 to shut down entirely, thenturn back on and enter the startup state 201, where data connectivitymay be re-established.

FIG. 6 depicts an exemplary procedure for checking and handling dataconnectivity errors. In addition to checking for loss of dataconnectivity through pinging of the ping server 106, the ping mechanism108 of the satellite terminal 102 may also have the RAB error monitor109 running concurrently in the RAB error monitoring state 206. In block601, the RAB error monitor 109 may be started. For example, when theping mechanism 108 transitions from the startup state 201 to the pingidle state 202, the ping mechanism 108 may concurrently enter the RABerror monitoring state 206, where the RAB error monitor 109 may bestarted.

In block 602, the RAB error monitor 109 may set a RAB error counter tozero. A RAB error counter may count the number of consecutive RAB errorsdetected by the RAB error monitor 109 without intervening successfuldata receipt or transmission. When the RAB error monitor 109 starts, noRAB errors may have been detected yet, so the RAB error counter may bestarted at zero. The RAB error counter may also be reset to zero when anindication of successful data receipt or transmission occurs, as anyfuture RAB errors would then not be consecutive with the previouslycounted RAB errors.

In block 603, the RAB error monitor 109 may receive an indication fromthe communications stack 110. The communications stack 110 maycommunicate with the RAB error monitor 109 through indications, whichmay be messages indicating, for example, recent activity by thecommunications stack 110.

In block 604, the RAB error monitor 109 may determine if the indicationis a data indication. If the satellite terminal 102 has recently sentdata to or received data from the satellite ground station 101, thecommunications stack 110 may send a data indication to the RAB errormonitor 109. If the indication received by the RAB error monitor 109 isa data indication, flow proceeds to block 605. Otherwise flow proceedsto block 606.

In block 605, the RAB error monitor 109 may set a “Data Indication” flagand note the time of receipt of the data indication. The “DataIndication” flag may indicate that data connectivity exists between thesatellite terminal 102 and satellite ground station 101, evidenced bythe recent sending or receiving of data. Flow may proceed from block 605back to block 602, where the RAB error counter may be reset.

In block 606, the RAB error monitor 109 may determine if the indicationis a RAB Establishment Error indication. If the satellite terminal 102has detected errors in data transmission to and from the satelliteground station 101, including, for example, excess dropped packets,corrupted data, and/or lack of data ability to send and/or receive data,the satellite terminal 102 may generate a RAB Establishment Errorindication. If the indication is a RAB Establishment Error indication,flow proceeds to block 607. Otherwise, flow proceeds back to block 603,where the RAB error monitor 109 may receive another indication from thecommunications stack 110.

In block 607, the RAB error monitor 109 may increment the RAB Errorcounter. If the data indication is a RAB Establishment Error indication,the RAB Error counter may incremented to track the number of consecutiveRAB Establishment errors detected by the RAB error monitor 109.

In block 608, the RAB error monitor 109 may determine if the maximumnumber of RAB failures has been reached. The maximum number of RABfailures may be a configurable number indicating the maximum number ofconsecutive RAB errors the RAB monitor needs to detect beforedetermining that data connectivity has been lost. The RAB error monitor109 may compare the RAB error count to the maximum number of RAB errorsto determine if the maximum has been reached. If the maximum number ofRAB errors has been reached, for example, the maximum number of RABfailures is six, and the RAB error counter is at six, flow proceeds toblock 609. Otherwise, flow proceeds back to block 603, where the RABerror monitor 109 may receive another indication from the communicationsstack 110.

In block 609, the RAB error monitor 109 may determine if a watchdog isstill active. If the watchdog is still active, flow proceeds to block610. Otherwise, flow proceeds to block 611.

In block 610, the RAB error monitor 109 may send a message to the pingmechanism 108 to enter the active ping state 203. The RAB error monitor109 may, using the watchdog, send the restart message to the pingmechanism 108. The restart message may cause the ping mechanism 108 totransition from the ping idle state 202 to the active ping state 203.Flow then loops back to block 602, where the RAB error counter may bereset and the RAB error monitor 109 may continue monitoring.

In block 611, the RAB error monitor 109 may directly call a functionrestart the communications stack 110. If the watchdog process is notactive, the RAB error monitor 109 may not be able to send the restartmessage to cause the ping mechanism 108 to enter the active ping state203. In order to restore data connectivity, the RAB error monitor 109may restart the communications itself, by directly calling the functionthat restarts the communication stack.

FIG. 7 depicts an exemplary procedure for determining if a connection isalways on. In block 701, the satellite terminal 102 may start checkingon the connections, or PDP contexts, between the satellite terminal 102and the satellite ground station 101, to determine if the connectionsare always-on connections.

In block 702, the satellite terminal 102 may determine if it is PacketSwitched (PS) attached. If the satellite terminal 102 is PS attached,flow proceeds to block 703. Otherwise, flow loops back to block 702,until the satellite terminal 102 is PS attached.

In block 703, the satellite terminal 102 may retrieve the next IPaddress in an Address Resolution Protocol (ARP) table. The ARP table maybe a table which lists previously contacted IP addresses and correlatedMedia Access Control (MAC) addresses.

In block 704, the satellite terminal 102 may determine if the IP addresshas been previously processed. If the IP address has been previouslyprocessed, for example, if the satellite terminal 102 has alreadychecked the IP address to determine if it is part of an always-onconnection or PDP context, flow proceeds back to block 703. Otherwise,flow proceeds to block 705.

In block 705, the satellite terminal 102 may determine if the IP addressbelongs to a User Terminal (UT). If the IP address is a UT's, flowproceeds back to block 703. Otherwise, flow proceeds to block 706.

In block 706, the satellite terminal 102 may determine if “Always On” isconfigured for the IP address. If “Always On” is not configured for theIP address, flow proceeds to block 707. Otherwise, flow proceeds toblock 708.

In block 707, the satellite terminal 102 may apply normal AutomaticContext Activation (ACA) processing to the IP address. The IP addressmay not be part of an always-on connection, and may only require normalACA processing.

In block 708, the satellite terminal 102 may determine if “Always On” isalready defined for the IP address. If “Always On” is already defined,then the IP address may already be part of an always-on connection, andflow proceeds to block 713. Otherwise, flow proceeds to block 709.

In block 709, the satellite terminal 102 may define a PDP context with“Always On” parameters and associate the PDP context with a local IPaddress. An always-on connection, or PDP context, may be established forthe IP address. This always-on connection may then be associated withthe local IP address for the satellite terminal 102, establishing analways-on connection between the satellite terminal 102 and thesatellite ground station 101.

In block 710, the satellite terminal 102 may send an activation message.The activation message may be sent to the satellite ground station 101and may indicate the activation of an always-on connection between thesatellite terminal 102 and the satellite ground station 101.

In block 711, an “Always On” timer may be started for the always-onconnection, a check time may be calculated, and “Always On” may bedefined for the IP address. The “Always On” timer may track how long the“Always On” connection is active, and the check time may be the amountof time that must elapse before attempting to reactivate the always-onconnection. “Always On” may be defined for the IP address so thatsatellite terminal 102 can determine that the IP address is part of analways-on connection and doesn't redefine a PDP context for the IPaddress in the future.

In block 712, the satellite terminal 102 may star an active “Always On”scan for the IP address. The active “Always On” scan may check thealways-on connection to ensure the PDP context for the always-onconnection is active and attempt to reactivate the PDP context for thealways-on connection if the always-on connection is found to beinactive.

In block 713, the satellite terminal 102 may determine if there are moreIP addresses in the ARP table. If there are more IP addresses in the ARPtable, flow proceeds back to block 703. Otherwise, flow proceeds toblock 714 and ends.

FIG. 8 depicts an exemplary procedure of an active scan for an always onconnection. Once an always-on connection has been started, the satelliteterminal 102 may continuously monitor the always-on connection to ensureit remains active. In block 801, the active “Always On” scan may bestarted for a PDP context.

In block 802 the satellite terminal 102 may determine if it is PSattached to the network. If it is PS attached, flow proceeds to block803. Otherwise, flow loops back to block 802 until it is PS attached.

In block 803, the satellite terminal 102 may determine if the PDPcontext is defined. If the PDP context for the always-on connection isdefined, flow proceeds to block 804. Otherwise flow loops back to block801.

In block 804, the satellite terminal 102 may determine if the PDPcontext is active. If the PDP context is active, for example, thealways-on connection is active and can be used to transmit and receivedata, flow loops back to block 801, as the always-on connection, or PDPcontext, is functioning and does not need to be reactivated. Otherwise,if the PDP context is not active, flow proceeds to block 805.

In block 805, the satellite terminal 102 may determine if the maximumnumber of attempts at reactivating the PDP context have already beenmade. The PDP context may have a reactivation attempts counter, whichmay track the number of time the satellite terminal 102 has attempted toreactive the PDP context. There may be a maximum number of attempts atreactivation that can be made for any given PDP context before thesatellite terminal 102 takes alternative action rather than attemptinganother reactivation. The maximum number of reactivation attempts may beany suitable number and may be configurable. If the satellite terminal102 has already made the maximum number of reactivation attempts, flowproceeds to block 806. Otherwise flow proceeds to block 807.

In block 806, the check time may set to, for example, 4 hours, and thereactivation attempts count may be set to zero. Once the maximum numberof reactivation attempts have been made, the satellite terminal 102 mayset the check time to a longer time period, such as, for example, 4hours, to prevent any more reactivation attempts during that timeperiod. This may prevent the satellite terminal 102 from wastingresources constantly attempting to reactivate a PDP context that keepsfailing, and from the using an unreliable PDP context for dataconnectivity. Flow then proceeds back to block 801.

In block 807, the satellite terminal 102 may determine if the check timehas expired. If the check time for PDP context has not expired, forexample, if the check time was set to 4 hours, and only 3 hours haveelapsed, flow proceeds back to block 801. Otherwise, if the check timehas expired, flow proceeds to block 808.

In block 808, the satellite terminal 102 may send a reactivation messageto the PDP context. The reactivation message may cause the inactive PDPcontext to be activated thereby restoring the always-on connection.

In block 809, the reactivation attempts counter may be incremented, andthe check time may be recomputed. The reactivation attempts counter maybe incremented every time a reactivation message is sent to reactivatethe PDP context thereby tracking the number of times the PDP context hasfailed and been reactivated. The check time may be recomputed, which maysend the amount of time that must pass before another reactivationattempt can be made for the PDP context. The check time may, forexample, increase linearly or exponentially with an increase in thereactivation attempts counter. This may result in greater and greateramounts of time being required to elapse between reactivation attemptsfor the PDP context thereby preventing the satellite terminal 102 fromwasting resources on frequent and closely spaced together reactivationattempts. Flow may proceed from block 809 back to block 801, where theactive “Always On” scan may continue monitoring the PDP context.

As used herein, a “computer” or “computer system” may be, for exampleand without limitation, either alone or in combination, a personalcomputer (PC), server-based computer, main frame, server, microcomputer,minicomputer, laptop, personal data assistant (PDA), cellular phone,pager, processor, including wireless and/or wire line varieties thereof,and/or any other computerized device capable of configuration forreceiving, storing and/or processing data for standalone applicationand/or over a networked medium or media. Examples of communication mediathat can be employed include, without limitation, wireless datanetworks, wire line networks, and/or a variety of networked media.

Computers and computer systems described herein may include operativelyassociated computer-readable media such as memory for storing softwareapplications used in obtaining, processing, storing and/or communicatingdata. It can be appreciated that such memory can be internal, external,remote or local with respect to its operatively associated computer orcomputer system. Memory may also include any means for storing softwareor other instructions including, for example and without limitation, ahard disk, an optical disk, floppy disk, DVD, compact disc, memorystick, ROM (read only memory), RAM (random access memory), PROM(programmable ROM), EEPROM (extended erasable PROM), and/or other likecomputer-readable media.

In general, computer-readable media may include any medium capable ofbeing a carrier for an electronic signal representative of data stored,communicated or processed in accordance with embodiments of the presentinvention. Where applicable, method steps described herein may beembodied or executed as instructions stored on a computer-readablemedium or media.

It is to be understood that the figures and descriptions have beensimplified to illustrate elements that are relevant for a clearunderstanding of the disclosed systems and methods, while eliminating,for purposes of clarity, other elements. Those of ordinary skill in theart will recognize, however, that these and other elements may bedesirable. However, because such elements are well known in the art, andbecause they do not facilitate a better understanding of the disclosedsystems and methods, a discussion of such elements is not providedherein. It should be appreciated that the figures are presented forillustrative purposes and not as construction drawings. Omitted detailsand modifications or alternative embodiments are within the purview ofpersons of ordinary skill in the art.

It can be appreciated that, in certain aspects of the disclosed system,a single component may be replaced by multiple components, and multiplecomponents may be replaced by a single component, to provide an elementor structure or to perform a given function or functions. Except wheresuch substitution would not be operative to practice certain embodimentsof the present invention, such substitution is considered within thescope of the present invention.

The examples presented herein are intended to illustrate potential andspecific implementations of the present invention. It can be appreciatedthat the examples are intended primarily for purposes of illustration ofthe invention for those skilled in the art. The diagrams depicted hereinare provided by way of example. There may be variations to thesediagrams or the operations described herein without departing from thespirit of the invention. For instance, in certain cases, method steps oroperations may be performed or executed in differing order, oroperations may be added, deleted or modified.

Furthermore, whereas particular embodiments of the invention have beendescribed herein for the purpose of illustrating the invention and notfor the purpose of limiting the same, it will be appreciated by those ofordinary skill in the art that numerous variations of the details,materials and arrangement of elements, steps, structures, and/or partsmay be made within the principle and scope of the invention withoutdeparting from the invention as described in the following claims.

It should be understood that various changes and modifications to thepresently preferred embodiments described herein will be apparent tothose skilled in the art. Such changes and modifications can be madewithout departing from the spirit and scope of the present subjectmatter and without diminishing its intended advantages. It is thereforeintended that such changes and modifications be covered by the appendedclaims.

1. A system for maintaining data connectivity in a satellitecommunications system comprising: a satellite terminal comprising a pingmechanism; a satellite ground station; and a ping server; wherein theping mechanism is configured to ping the ping server and restore dataconnectivity between the satellite terminal and the satellite groundstation.
 2. The system of claim 1, wherein the ping server is configuredto return a ping message from the satellite terminal upon receiving theping message.
 3. The system of claim 1, wherein the ping mechanism isconfigured to restart a communications stack of the satellite terminalwhen a ping message sent to the ping server is not returned by the pingserver.
 4. The system of claim 3, wherein the satellite terminalcomprises a RAB error monitor.
 5. The system of claim 4, wherein theping mechanism is configured to restart the communications stack of thesatellite terminal when the RAB error monitor detects a configurednumber of consecutive data errors.
 6. The system of claim 5, wherein theping mechanism is configured to reboot the satellite terminal when thecommunications stack fails to restart.
 7. The system of claim 1, whereinthe ping server is co-located with a data server.
 8. The system of claim1, wherein the ping mechanism is configured to ping the ping server whena timer expires.
 9. The system of claim 4, wherein the ping mechanism isconfigured to ping the ping server when the ping mechanism receives arestart message from the RAB error monitor.
 10. The system of claim 8,wherein the ping mechanism is configured to ping the ping server when atimer expires and when a ping required is set.
 11. The system of claim10, wherein the timer is set to count down from a time greater than atypical interval between data transmissions between the satellite groundstation and the satellite terminal.
 12. A method for maintaining dataconnectivity in a satellite communications system comprising: starting atimer; sending a ping message to a ping server on expiration of thetimer; determining if the ping message was returned by the ping server;and if the message was returned by the ping server, resetting the timer,and if the message was not returned by the ping server, restarting acommunications stack.
 13. The method of claim 12, further comprisingsending a message to a ping server on expiration of the timer only ifthere has been no successful sending of data to or receiving of datafrom a satellite ground station within a configured amount of time. 14.The method of claim 12, further comprising: receiving a restart messagefrom an RAB error monitor; and restarting the communication stack. 15.The method of claim 12, further comprising: determining if thecommunications stack was previously restarted; and if the communicationsstack was previously restarted, rebooting a satellite terminal, and ifthe communications stack was not previously restarted, restarting thecommunications stack.
 16. The method of claim 12, further comprising,when a PDP context is not active and was not active and has not failedmore than configured number of times, transitioning to an idle state toallow time for the PDP context to be restarted.
 17. The method of claim16, wherein the PDP context is restarted by an active always-on scan.18. The method of claim 12, wherein the timer is set to count down froman interval greater than typical interval between data transmission toand from a satellite ground station.